Skip to content

Conversation

@nwnt
Copy link
Contributor

@nwnt nwnt commented Sep 19, 2025

Description of your changes

Move the managed resource VAP and its binding installation out of CRD installer. They are now installed by the hub and member agents. For hub, they are installed after the hub agent starts and never removed. For member, they are installed during member join and removed during member leave.

Fixes # N/A

I have:

  • Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Unit tests and E2E tests.

Special notes for your reviewer

@nwnt nwnt changed the title Vap lifecycle management fix: move managed resource VAP out of CRDinstaller Sep 19, 2025
@nwnt nwnt force-pushed the vap-lifecycle-management branch 2 times, most recently from 88d7c79 to ccf584e Compare September 29, 2025 21:52
@nwnt nwnt force-pushed the vap-lifecycle-management branch 2 times, most recently from 47ed11d to 129bf0e Compare September 29, 2025 22:29
@nwnt nwnt force-pushed the vap-lifecycle-management branch from 129bf0e to 323249f Compare September 29, 2025 22:38
@nwnt nwnt force-pushed the vap-lifecycle-management branch from 0e8458c to 6166175 Compare September 30, 2025 00:35
Nont added 2 commits September 29, 2025 19:44
Signed-off-by: Nont <[email protected]>
Signed-off-by: Nont <[email protected]>
@nwnt nwnt merged commit 2bf8667 into Azure:main Oct 2, 2025
17 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants